Apparatus and method for validating application deployment topology in cloud computing environment

ABSTRACT

The present invention relates to an apparatus and a method for validating application deployment topology in a cloud environment. There is provided an apparatus for validating application deployment topology in a cloud environment comprising: a topology skeleton generator configured to generate, based on multiple VMs and script packages running on the VMs created by a user and required to deploy an application as well as running order of script packages and data dependency between script packages set by the user, a topology skeleton that comprises at least scripts of script packages of respective VMs and running order of the script packages; and a simulator configured to simulate a runtime environment in the cloud environment at the apparatus, thereby validating the running order and data dependency with respect to the topology skeleton, wherein the simulator is installed in the apparatus by using a simulator installation package retrieved from the cloud environment.

BACKGROUND

The present invention generally relates to the field of computer, andmore specifically, to an apparatus and a method for validatingapplication deployment topology in cloud computing environment.

PaaS is the abbreviation for Platform-as-a-Service, and it is a businessmodel in which a server platform is provided as a service. A serviceproviding a software program through network is called SaaS (Software asa Service), whereas in the cloud computing era, providing acorresponding server platform or developing environment as a service isPaaS. The service provided by PaaS differs from other services in thatPaaS provides a basic platform instead of a certain application. Intraditional concept, a platform is the basis of providing services tothe outside. In general, as the basis of application system deployment,a platform is built and maintained by an application service provider.However, PaaS subverts this concept. A special platform service providerbuilds and operates the basic platform, and provides the platform to anapplication system operator as a service.

A developer (a PaaS' user) may deploy complicated topology to installmiddleware, applications, cloud services, etc. The developer utilizes,for example, an integrated developing environment to create a topologymodel which corresponds to a kind of deployment of an application in ahardware server. FIG. 4 shows an example of correspondence between adeployment topology model and hardware servers. Three Virtual Machines(VMs) are shown in the upper part of FIG. 4, wherein VM Custom Node isdeployed on two servers in actual deployment in the lower part of FIG.4.

In general, it is necessary to run script packages on respective VMs tocomplete deployment. FIG. 5 shows a view of an example of running scriptpackages on three VMs to deploy applications. In FIG. 5, in the VM Dmgr(Deployment Manager), script packages “1. Install Application ServerBinaries”, “2. Create Web Server” and “4. Add Member to Cluster” are tobe executed; in the VM Custom Node, script packages “1. InstallApplication Server Binaries” and “3. Add Custom Node to Dmgr” are to beexecuted; and in the VM HTTP server, a script package “1. Install HTTPServer Binaries” is to be executed. In FIG. 5, for example, execution ofthe script package 2 in the VM Dmgr needs the output parameter IHS_IP ofthe script package 1 in the VM HTTP server as its input parameter,execution of the script package 3 in the VM Custom Node needs fouroutput parameters (DMGR_IP, DMGR_PORT, DMGR_USERNAME, DMGR_PASSWORD) ofthe script package 2 in the VM Dmgr as its input parameters, and thescript package 4 in the VM Dmgr needs to be executed after the scriptpackage 3 in the VM Custom Node. Therefore, these script packages needto be executed in a specific order. In FIG. 5, dashed line arrows areused to show the execution order of script packages across VMs, andbubbles that branch from dashed line arrows are used to show datadependency between script packages.

A user sets up said order and data dependency during design period.However, at present, said order and data dependency can only bevalidated at runtime, e.g., after various VMs are launched. That is, atpresent, validation of said order and data dependency needs to beperformed in actual deployment. However, it takes a long time tovalidate the order and data dependency of script packages of VMs atruntime. For example, deployment of BPM (Business Process Management)Pattern needs to take about 1 hour and 20 minutes, and it hascomplicated execution order and data dependency. When being deployed,some script packages may not export necessary data, so other scriptpackages that depend on these script packages will run to error. Theuser needs to find out the reason for the failure from a large volume oflog files and multiple VMs, which is very time-consuming and fussy work.Further, in a case where the error has been found, it is necessary toperform time-consuming deployment again after correcting the error(e.g., modifying the script package). Also, in this process, othererrors may occur. In brief, at present, application deployment performedby the PaaS' user is very time-consuming.

SUMMARY

In order to solve the above problems, one of objects of the presentinvention is to provide an apparatus and a method capable of validatingapplication deployment topology in a cloud computing environment beforebeing deployed in the cloud computing environment.

According to one aspect of the present invention, there is provided anapparatus for validating application deployment topology in a cloudcomputing environment, comprising: a topology skeleton generatorconfigured to generate, based on multiple VMs and script packagesrunning on the VMs created by a user and required to deploy anapplication of the user, as well as running order of said scriptpackages and data dependency between said script packages set by theuser, a topology skeleton that comprises at least scripts of scriptpackages of respective VMs and running order of the script packages; anda simulator configured to simulate a runtime environment in the cloudcomputing environment at the apparatus, thereby validating said runningorder and data dependency with respect to said topology skeleton,wherein said simulator is installed in said apparatus by using asimulator installation package retrieved from the cloud computingenvironment.

According to another aspect of the present invention, there is provideda method for validating application deployment topology in a cloudcomputing environment at an apparatus, comprising: based on multiple VMsand script packages running on the VMs created by a user and required todeploy an application of the user, as well as running order of saidscript packages and data dependency between said script packages set bythe user, generating a topology skeleton that comprises at least scriptsof script packages of respective VMs and running order of the scriptpackages; and configuring a simulator to simulate a runtime environmentin the cloud computing environment at said apparatus, thereby validatingsaid running order and data dependency with respect to said topologyskeleton, wherein said simulator is installed in said apparatus by usinga simulator installation package retrieved from the cloud computingenvironment.

With the apparatus and the method for validating deployment topology inthe cloud according to the present invention, it is possible to provide,at the client side relative to the cloud server platform, the PaaS' userwith a light-weight appliance to help the user quickly and easilyvalidate execution order and data dependency at runtime. In addition,the apparatus and the method according to the present invention canoffload the deployment validation workload from the cloud platform sideto the client side, thereby improving the performance of the cloudplatform. In addition, the apparatus and the method according to thepresent invention can save a great deal of time that is taken to dig outthe failure reason during deployment from large volumes of logs on thecloud platform and lots of virtual machines at runtime.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Through the more detailed description of some embodiments of the presentdisclosure in the accompanying drawings, the above and other objects,features and advantages of the present disclosure will become moreapparent, wherein the same reference generally refers to the samecomponents in the embodiments of the present disclosure.

FIG. 1 shows a cloud computing node according to an embodiment of thepresent invention;

FIG. 2 shows a cloud computing environment according to an embodiment ofthe present invention;

FIG. 3 shows abstraction model layers according to an embodiment of thepresent invention;

FIG. 4 shows an example of a correspondence between a deploymenttopology model and hardware servers;

FIG. 5 is a view showing an example of graphic representation of atopology design for deploying applications;

FIG. 6 is a schematic view showing an apparatus for validatingapplication deployment topology in a cloud computing environmentaccording to an embodiment of the present invention;

FIG. 7 shows an example of a topology skeleton in the form of treefolder generated by a topology skeleton generator;

FIG. 8 shows exemplary content of script files under a script packagefolder “2_Create_Web_Server” in the VM Dmgr;

FIG. 9A shows an example in which a reporter reports a data dependencyerror to a user;

FIG. 9B shows an example in which a reporter reports a syntax error or aspelling error to the user; and

FIG. 10 is a flowchart showing a method for validating applicationdeployment topology in a cloud computing environment at an apparatus 100according to an embodiment of the present invention.

DETAILED DESCRIPTION

Some preferable embodiments will be described in more detail withreference to the accompanying drawings, in which the preferableembodiments of the present disclosure have been illustrated. However,the present disclosure can be implemented in various manners, and thusshould not be construed to be limited to the embodiments disclosedherein. On the contrary, those embodiments are provided for the thoroughand complete understanding of the present disclosure.

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 1, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via Input/Output(I/O) interfaces 22. Still yet, computer system/server 12 cancommunicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 20. As depicted, network adapter 20communicates with the other components of computer system/server 12 viabus 18. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 12. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 2, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 2 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 3, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 2) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 3 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include mainframes, in oneexample IBM® zSeries® systems; RISC (Reduced Instruction Set Computer)architecture based servers, in one example IBM pSeries® systems; IBMxSeries® systems; IBM BladeCenter® systems; storage devices; networksand networking components. Examples of software components includenetwork application server software, in one example IBM WebSphere®application server software; and database software, in one example IBMDB2® database software. (IBM, zSeries, pSeries, xSeries, BladeCenter,WebSphere, and DB2 are trademarks of International Business MachinesCorporation registered in many jurisdictions worldwide).

Virtualization layer 62 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one example, management layer 64 may provide the functions describedbelow. Resource provisioning provides dynamic procurement of computingresources and other resources that are utilized to perform tasks withinthe cloud computing environment. Metering and Pricing provide costtracking as resources are utilized within the cloud computingenvironment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal provides access to the cloud computing environment forconsumers and system administrators. Service level management providescloud computing resource allocation and management such that requiredservice levels are met. Service Level Agreement (SLA) planning andfulfillment provide pre-arrangement for, and procurement of, cloudcomputing resources for which a future requirement is anticipated inaccordance with an SLA.

Workloads layer 66 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation; software development and lifecycle management; virtualclassroom education delivery; data analytics processing; transactionprocessing; and moving desktop.

The present invention relates to the virtualization layer 62.

FIG. 6 is a schematic view showing an apparatus 100 for validatingapplication deployment topology in a cloud computing environmentaccording to an embodiment of the present invention. The apparatus 100may be any computing apparatus that can run VMs. In one embodiment, theapparatus 100 may be a client relative to a cloud server platform (acloud computing environment). In FIG. 6, the apparatus 100 includes atopology skeleton generator 110 and a simulator 120. The topologyskeleton generator 110 is configured to generate, based on multiple VMsand script packages running on the VMs created by the user and requiredto deploy the user's application as well as running order of said scriptpackages and data dependency between said script packages set by theuser, a topology skeleton that includes at least scripts of scriptpackages of respective VMs and running order of the script packages. Thesimulator 120 is configured to simulate a runtime environment in thecloud computing environment at the apparatus 100, thereby validatingsaid running ordering and data dependency with respect to said topologyskeleton. Said simulator is installed in the apparatus 100 by using asimulator installation package retrieved from the cloud computingenvironment.

In one embodiment of the present invention, the user may create VMs andscript packages by using GUI (Graphical User Interface) of a topologydesigner in the integrated developing environment of the apparatus 100(with operations, e.g., drag-and-drop, connect, etc.), and may definerunning order of script packages and data dependency between scriptpackages. For example, the user first creates multiple VMs required todeploy the user's application. For example, as shown in the upper partof FIG. 4, the user creates three VMs in the graphic form in thisexample. In another embodiment, for example, VMs and script packagescreated by the user may be in a data structure such as a table, etc.Then, the user creates script packages running on respective VMs in thetopology designer, and defines running order of script packages and datadependency between script packages. FIG. 5 is an example of the topologydesign obtained by using the topology designer. The topology designincludes graphic representation (as shown by the round-corneredrectangles in FIG. 5) of multiple VMs and script packages running on theVMs created by the user. The topology design also includes running order(as shown by the dashed lines in FIG. 5) of script packages and datadependency (as shown by the rectangular bubble in FIG. 5) between scriptpackages set by the user.

The topology designer that provides the graphic interface simplifies thedifficulty of user's design. For example, products such as the PivotalOne of the Pivotal company and the Cloud Foundry of the VMware company,etc, provide the topology designer which has functions described above.

The topology skeleton generator 110 generates, based on said topologydesign, a topology skeleton that includes at least scripts in scriptpackages of respective VMs and running order of the script packages. Inone embodiment of the present invention, the topology skeleton may be inthe form of tree folder. It includes VMs and script packages.Specifically, each VM corresponds to a VM folder under the root folder,each script package running on the VM corresponds to a subfolder underthe VM folder, and each subfolder contains a script.

For example, FIG. 7 shows an example of a topology skeleton in the formof tree folder generated by the topology skeleton generator 110. Thetopology skeleton in FIG. 7 is generated by the topology skeletongenerator 110 based on the topology design in FIG. 5. Specifically, theroot folder “VMs” includes three VM folders (the icon of which has alabel “V”), whose names are VM_CustomNode, VM Dmgr and VM_HTTPServer.These three VM folders correspond to the VM Custom Node, the VM Dmgr andthe VM HTTP Server in FIG. 5, respectively. The VM folder includessubfolders (the icon of which has a label “S”) corresponding torespective script packages running on the VM. For example, in FIG. 7,the VM folder VM_CustomNode includes two subfolders, i.e., 1_Install_(—)Application_Binaries and 3_Add_Custom_Node_to_Dmgr, which correspond tothe two corresponding script packages in the VM Custom Node in FIG. 5,respectively. In addition, each subfolder corresponding to a scriptpackage contains a script file. Serial numbers contained in the names ofsubfolders described above represent execution order of script packagesof respective VMs. In FIG. 7, said script file is, for example, run.py.The name of the script is merely exemplary, and any other names may beadopted in other embodiments.

FIG. 8 shows exemplary content of the script “run.py” under the scriptpackage folder “2_Create_Web_Server” in the VM Dmgr. The script includesan import method for getting input parameters from the outside and anexport method for exporting parameters to the outside. The script mayalso include an implement method for implementing the function of thescript specifically. In the example of the script “run.py” shown in FIG.8, the import method import( ) is used to get input parameters (such asinitial parameters) from the outside (i.e., the environment); theimplement method implement( ) is used to implement the function of thescript specifically, such as installing middleware binaries, etc; andthe export method export( ) is used to export parameters to the outsideto be used by other scripts.

In one embodiment, said script is a default script (i.e., a scriptautomatically generated by the apparatus 100), and the apparatus 100 mayalso include an editor. The editor may be used by the user to edit atleast a part of said default script. For example, the user my use theeditor to edit the implement( )method in the script in FIG. 8 to addcontent to be implemented, such as codes for installing middlewarebinaries, etc. In FIG. 8, the function of the implement( )method is toinstall a Web server. This portion of codes may be added by the userthrough the editor and are omitted in FIG. 8. In the implement( )methodin FIG. 8, codes for assigning values to four parameters to be exportedare included.

In the above example given, the names of the import method, theimplement method and the export method are not limited to import( )implement( ) and export( ) Other names may also be adopted, as long asthey can be identified and can function in the same way.

In the above example, the topology skeleton is described in the form oftree folder. In another embodiment, the topology skeleton may be inother forms, such as XML file or graphic representation, etc.

After the topology skeleton is generated by the topology skeletongenerator 110, the simulator 120 simulates the runtime environment inthe cloud computing environment at apparatus 100, thereby validatingsaid running order and data dependency with respect to said topologyskeleton.

The simulator 120 is installed in the apparatus 100 by using a simulatorinstallation package retrieved from the cloud computing environment. Inone embodiment according to the present invention, the simulatorinstallation package is updated at the cloud side in response to changesin the cloud environment. Therefore, the simulator installation packagedownloaded from the cloud side (the cloud platform) can always reflectthe current runtime environment of the cloud platform. In oneembodiment, when the simulator installation package is updated at thecloud platform, the apparatus 100 is instructed to download it. In oneembodiment, the simulator installation package is in the form of binary;in another embodiment, the simulator installation package is in the formof codes that may be interpreted and executed or compiled and executed.After the simulator installation package is downloaded to the apparatus100, it is installed and set at the apparatus 100, thereby implementingthe simulator 120. In one embodiment according to the present invention,the simulator 120 is embodied as one button or a group of buttons in theintegrated developing environment in the apparatus 100. Simulation isperformed by pressing said buttons. In another embodiment, the simulator120 is embodied as a stand-alone module in the apparatus 100.

In one embodiment according to the present invention, the simulator 120is configured to launch, for each VM, a process or thread to performsaid simulation. Hereinafter, only the thread is taken as an example forexplanation, but it is obvious that the process is also within the scopeof the present invention.

The case in FIGS. 5 and 7 will be taken as an example for explanation.As for the example in FIGS. 5 and 7, the simulator 120 launches threethreads to simulate the three VMs in FIG. 5. In one embodiment accordingto the present invention, validating said running order includesexecuting respective scripts in order in corresponding processes orthreads according to the running order included in said topologyskeleton. Specifically, according to the order of serial numbers in thenames of script package folders in FIG. 7, respective launched threadsexecute script files in script packages. For example, three threads (athread 1 corresponds to the VM Custom Node, a thread 2 corresponds tothe VM Dmgr, and a thread 3 corresponds to the VM HTTP Server) executescript files under folders VM_CustomNode\1_Install_Application_Binaries,VM_Dmgr\1_Install_Application_Binaries and1_Install_HTTP_Server_Binaries in parallel. After the thread 3 executesthe script file under the 1_Install_HTTP_Server_Binaries folder, thethread 2 executes the script file under the 2_Create_Web_Server folder;after the thread 2 executes the script file under the2_Create_Web_Server folder, the thread 1 executes the script file underthe 3_Add_Custom_Node_to Dmgr folder; after the thread 1 executes thescript file under the 3_Add_Custom_Node_to_Dmgr folder, the thread 2executes the script file under the 4_Add_Member_to_Cluster folder.

In one embodiment according to the present invention, validating datadependency includes running the import method and the export method inrespective scripts to check parameters defined in said import method andexport method. For example, checking parameters defined in said importmethod and export method includes checking at least one of the number,the names and the value constraints of said parameters. The case inFIGS. 5 and 7 will be taken as an example for explanation. In FIGS. 5and 7, the script file under the 3_Add_Custom_Node_to_Dmgr folder needsto be executed after the script file under the 2_Create_Web_Serverfolder, and there is data dependency between them. Specifically, fourparameters need to be transferred (see FIG. 5). It is assumed that theexport( )method of the script file under the 2_Create_Web_Server folderis:

def export( ):

sys.export[‘DMGR_IP’]

sys.export[‘DMGR_PORT’]

and the import( )method of the script file under the3_Add_Custom_Node_to_Dmgr folder is:

def import( ):

DMGR_IP=sys.parameters[‘DMGR_IP’]

DMGR_PORT=sys.parameters[‘DMGR_PORT’ ]

DMGR_USERNAME=sys.parameters[‘DMGR_USERNAME’]

DMGR_PASSWORD=sys.parameters[‘DMGR_PASSWORD’]

whereupon through simulation at the apparatus 100, it can be found thatthe export method of the script package “2. Create Web Server” exportsonly two of four input parameters required by the script package “3. AddCustom Node to Dmgr”. That is, when actual deployment is performedaccording to the current topology design, errors will occur because datadependency is not satisfied. With one embodiment of the presentinvention, the problem can be found and solved at the client side beforeactual deployment, so that a great deal of time can be saved for actualdeployment.

In one embodiment, in addition to the number of the parameters, it isalso possible to check the names of the parameters defined in importmethods and export methods of script packages that have data dependencyto find unmatched parameters. For example, the parameter USERNAME in theexport method of the script package 1 and the parameter SUBSCRIBERNAMEin the import method of the script package 2 that depends on the scriptpackage 1 belong to a case where parameters' names do not match. Inanother embodiment, it is also possible to check, according to the typesof the parameters, the value constraints of the parameters transferredbetween script packages. For example, the IP parameter should be in theform of four numeric values spaced apart by “.”, such as “192.168.1.1”,the PORT parameter should be a numeric value, and the USERNAME andPASSWORD parameters should be character strings. Transferring ofparameters that violate value constraints may also be considered as notsatisfying data dependency.

The above describes checking of import methods and export methods inscript files. In one embodiment according to the present invention, thesimulator 120 is configured to not run the implement method inrespective scripts but only check at least one of the syntax error andthe spelling error in the implement method. That is, the simulator 120only executes the import method and the export method in a script file,but not run the implement method in the script file. This is becausesome functions (e.g., actual installation of middleware) of implementmethods cannot be executed in the apparatus 100. When being deployed onthe cloud platform, all of the import method, the export method and theimplement method will be executed. By skipping the implement method atthe apparatus 100, execution of simulation may be accelerated. On theother hand, by checking syntax errors and/or spelling errors in contentadded to the implement method by the user through the editor in programlevel, errors can be found in advance, and it is possible to avoiderrors occurring during actual deployment, which wastes a great deal oftime.

In one embodiment according to the present invention, the apparatus 100also includes a reporter configured to report to the user at least oneof the following errors found in the simulation procedure of thesimulator: data dependency error, syntax error and spelling error. FIG.9A shows an example in which the reporter reports a data dependencyerror to the user. In FIG. 9A, the following example is shown: thenumber of the parameters in the export method of the script package “2.Create Web Server” and that of the import method of the script package“3. Add Custom Node to Dmgr” described above are not identical. In thiscase, the simulator 120 finds the data dependency error, and thereporter reports the data dependency error to the user. Specifically, inFIG. 9A, the reporter highlights (or displays in a different color) thearrow connected from the script package “2. Create Web Server” to thescript package “3. Add Custom Node to Dmgr” (e.g., displayed as a thickarrow), and displays the former's output parameters and the latter'sinput parameters. In this way, the user may easily recognize and locatethe data dependency error. FIG. 9B shows an example in which thereporter reports a syntax error or a spelling error to the user. In FIG.9B, for example, when the simulator 120 finds a syntax error or aspelling error in the implement( )method of the script file of thescript package “2. Create Web Server”, the reporter highlights (ordisplays in a different color) the graphic representation of the scriptpackage “2. Create Web Server”, so that the user may eliminate thesyntax error or the spelling error in the script package by clicking thegraphic representation of the script package to edit the script of thescript package. By doing so, it is possible to avoid errors occurringduring actual deployment due to the fact that the syntax error or thespelling error is contained in the content added in the implement methodby the user.

According to one embodiment of the present invention, the apparatus 100may also include a deployer. When no error is found in the simulationexecuted by the simulator 120, the deployer may deploy the applicationto the cloud platform according to said topology design.

FIG. 10 is a flowchart showing a method for validating applicationdeployment topology in a cloud computing environment at the apparatus100 according to an embodiment of the present invention. The validatingmethod includes a topology skeleton generation step 1010 and asimulation execution step 1020. In the topology skeleton generation step1010, based on multiple VMs and script packages running on the VMscreated by the user and required to deploy the user's application aswell as running order of said script packages and data dependencybetween said script packages set by the user, a topology skeleton isgenerated, and the topology skeleton includes at least scripts of scriptpackages of respective VMs and running order of the script packages. Inthe simulation execution step 1020, a simulator is configured tosimulate a runtime environment in the cloud computing environment atsaid apparatus, thereby validating said running order and datadependency with respect to said topology skeleton, wherein saidsimulator is installed in the apparatus by using a simulatorinstallation package retrieved from the cloud computing environment.Since the process flow has been described in detail with respect to theapparatus 100 hereinabove, explanation is not repeated here.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

What is claimed is:
 1. An apparatus for validating applicationdeployment topology in a cloud computing environment comprising: atopology skeleton generator configured to generate, based on multipleVMs and script packages running on the VMs created by a user andrequired to deploy an application of the user as well as running orderof the script packages and data dependency between the script packagesset by the user, a topology skeleton that comprises at least scripts ofscript packages of respective VMs and running order of the scriptpackages, wherein the script comprises an import method for gettinginput parameters from the outside and an export method for exportingparameters to the outside; and a simulator configured to simulate aruntime environment in the cloud computing environment at the apparatus,thereby validating the running order and data dependency with respect tothe topology skeleton, wherein the simulator is installed in theapparatus by using a simulator installation package retrieved from thecloud computing environment, and wherein validating data dependencycomprises running the import method and the export method in respectivescripts to check parameters defined in the import method and exportmethod.
 2. The apparatus according to claim 1, wherein the topologyskeleton is in the form of tree folder, each VM corresponds to a VMfolder under the root folder, each script package running on a VMcorresponds to a subfolder under the VM folder, and each subfoldercontains a script.
 3. The apparatus according to claim 1, wherein thescript is a default script, and the apparatus also comprises an editor,which may be used by the user to edit at least a part of the defaultscript.
 4. The apparatus according to claim 1, wherein the simulatorinstallation package is updated at the cloud side in response to changesin the cloud environment.
 5. The apparatus according to claim 1, whereinthe simulator is configured to launch, for each VM, a process or threadto perform the simulation.
 6. The apparatus according to claim 5,wherein validating the running order comprises executing respectivescripts in order in corresponding processes or threads according to therunning order included in the topology skeleton.
 7. The apparatusaccording to claim 1, wherein the script also comprises an implementmethod for implementing the function of the script specifically, and thesimulator is configured to not run the implement method in respectivescripts but only check at least one of syntax error and spelling errorin the implement method.
 8. The apparatus according to claim 1, furthercomprising a reporter configured to report to the user at least one ofthe following errors found in the simulation procedure of the simulator:data dependency error, syntax error and spelling error.
 9. The apparatusaccording to claim 1, wherein checking parameters defined in the importmethod and export method comprises checking at least one of the number,the names and the value constraints of the parameters.
 10. A method forvalidating application deployment topology in a cloud computingenvironment at an apparatus comprising: based on multiple VMs and scriptpackages running on the VMs created by a user and required to deploy anapplication of the user as well as running order of the script packagesand data dependency between the script packages set by the user,generating a topology skeleton that comprises at least scripts of scriptpackages of respective VMs and running order of the script packages,wherein the script comprises an import method for getting inputparameters from the outside and an export method for exportingparameters to the outside; and configuring a simulator to simulate aruntime environment in the cloud computing environment at the apparatus,thereby validating the running order and data dependency with respect tothe topology skeleton, wherein the simulator is installed in theapparatus by using a simulator installation package retrieved from thecloud computing environment, and wherein validating data dependencycomprises running the import method and the export method in respectivescripts to check parameters defined in the import method and exportmethod.
 11. The method according to claim 10, wherein the topologyskeleton is in the form of tree folder, each VM corresponds to a VMfolder under the root folder, each script package running on a VMcorresponds to a subfolder under the VM folder, and each subfoldercontains a script.
 12. The method according to claim 10, wherein thescript is a default script, and the user may use an editor included inthe apparatus to edit at least a part of the default script.
 13. Themethod according to claim 10, wherein the simulator installation packageis updated at the cloud side in response to changes in the cloudenvironment.
 14. The method according to claim 10, wherein the simulatoris configured to launch, for each VM, a process or thread to perform thesimulation.
 15. The method according to claim 14, wherein validating therunning order comprises executing respective scripts in order incorresponding processes or threads according to the running orderincluded in the topology skeleton.
 16. The method according to claim 10,wherein the script also comprises an implement method for implementingthe function of the script specifically, and the simulator is configuredto not run the implement method in respective scripts but only check atleast one of syntax error and spelling error in the implement method.